Can we use the same code for both this and the appbar? The way it is now has quite abit of code smell, onScheduleTask has different meaning depending on the context, we need to decouple it, my ideas are either

1. Have 2 different callback explicitly, for create and edit, then both here and appbar can use the same code.
2. Use different components, i.e. have a EditTask component, it can use CreateTaskForm internally but with some differences in behavior and text.

4dece1e

Add docs for these 2 props and schedule. iiuc, only onEditScheduleTask is used in "edit" mode, which is controlled by the schedule prop and onScheduleTask is used otherwise. They are mutually exclusive and will never be used together.

Better would be to refactor this to use the micro app hooks, the task form should be able to handle all the api calls itself and all these callbacks should be able to be replaced with a single onClose callback. But I leave it up to you if you want to do the refactor now.

they technically can be used together, just that we choose not to provide a callback in whichever place we are creating a task form, i.e. the edit schedule component can also provide onScheduleTask but because of the function itself, we choose not to provide it.

yeah using hooks will be ideal, I will help look into it when we finally merge react components and dashboard

edit: more specifically, buttons will be rendered, based on the availability of these callback functions, if both are provided, both buttons will be rendered.